The SMS must produce audit records containing information to establish the outcome of events associated with detected harmful or potentially harmful traffic, including, at a minimum, capturing all associated communications traffic by sending all audit and system logs to a centralized syslog server.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-242182	TIPP-IP-000160	SV-242182r710346_rule		Medium

Description
Associating event outcome with detected events in the log provides a means of investigating an attack or suspected attack. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The logs should identify what servers, destination addresses, applications, or databases were potentially attacked by logging communications traffic between the target and the attacker. All commands that were entered by the attacker (such as account creations, changes in permissions, files accessed, etc.) during the session should also be logged.

Description

Associating event outcome with detected events in the log provides a means of investigating an attack or suspected attack. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The logs should identify what servers, destination addresses, applications, or databases were potentially attacked by logging communications traffic between the target and the attacker. All commands that were entered by the attacker (such as account creations, changes in permissions, files accessed, etc.) during the session should also be logged.

STIG	Date
Trend Micro TippingPoint IDPS Security Technical Implementation Guide	2021-06-09

Details

Check Text ( C-45457r710087_chk )
1. In the Trend Micro SMS interface, go to the "Admin" tab, and select "Server Properties". 2. Select the "syslog" tab. If a syslog server is not configured to send the following audit logs, this is a finding: - Device Audit - Device System - SMS Audit - SMS system

Fix Text (F-45415r710088_fix)
1. In the Trend Micro SMS interface, go to the "Admin" tab, and select "Server Properties". 2. Select the "syslog" tab. Click "New". 3. Under syslog server type the hostname or IP address of the syslog server. 4. Click TCP to ensure logging data is queued in the case of disconnection of the syslog server. 5. Type the port used by the centralized logging server (traditionally it is port 514). 6. Under log type, select Device Audit. 7. Under facility click "Log Audit". 8. Click Event timestamp under "Include Timestamp in Header". 9. Select "include SMS hostname in header". Repeat this three more times changing the Log Type to include Device System, SMS Audit, and SMS System.

Fix Text (F-45415r710088_fix)

1. In the Trend Micro SMS interface, go to the "Admin" tab, and select "Server Properties".
2. Select the "syslog" tab. Click "New".
3. Under syslog server type the hostname or IP address of the syslog server.
4. Click TCP to ensure logging data is queued in the case of disconnection of the syslog server.
5. Type the port used by the centralized logging server (traditionally it is port 514).
6. Under log type, select Device Audit.
7. Under facility click "Log Audit".
8. Click Event timestamp under "Include Timestamp in Header".
9. Select "include SMS hostname in header".
Repeat this three more times changing the Log Type to include Device System, SMS Audit, and SMS System.